home *** CD-ROM | disk | FTP | other *** search
- *** Parallel Port Mode and TransCD Timing
- The IBM PC compatible parallel (printer) port was originally designed
- for IBM PC/XT. The signal quality and speed of the parallel port was
- not an issue because the parallel port was able to keep up with the
- relatively slow CPU when transferring data between the CPU and the
- devices connected to the port.
-
- Since then, the performance of the CPU has been dramatically improved
- with the introduction of the 486's and Pentium's, while the parallel
- port itself stays pretty much the same. The same parallel port still
- works for the printer devices because of the relatively slow transfer
- speed of the printer. However, with a high-speed device, such as a
- TransCD connected, the parallel port may find itself not able to keep
- up with the high-speed data transfer between the device and the CPU.
-
- Not all parallel ports are alike, especially when high-speed transfer
- is concerned. Some can be pushed to the limit; some perform badly when
- pushed. Fortunately in most cases, an workaround can be found. Please
- try the items below individually or in combination:
-
- *** 1. Change Parallel Port Mode ***
- Many machines, especially Pentium's, come with manufacturer's CMOS
- default setup to non-EPP mode for parallel port. Some computers, when
- set to uni-directional port, shut off certain signals which may cause
- the TransCD not to work. It is a good idea to change into EPP, but not
- ECP or ECP/EPP mode. The EPP mode does provide better signal quality. If
- EPP mode is not available, try Bi-dir (Bi-directional) mode if it exists.
-
- *** 2. Adjust TransCD Timing ***
- The following applies to non-EPP mode only as /T is ignored in EPP mode.
- If we slow down the data transfer slightly during access to the parallel
- port, the port may have enough time to allow data to become ready. The
- TransCD Device Driver provides a timing option for this purpose. If the
- driver is loaded via a DEVICE entry in the CONFIG.SYS file, append the
- line with the "/T:x" option where a good value of 'x' to try is 5, other
- values are 10, 3, or 2 (default=0 if no /T is specified). For example:
- DEVICE=C:\TCD-IDE\TCD-IDE.SYS /D:TCD-IDE$ /T:5
- (or) DEVICE=C:\TRANSCD\TRANSCD.SYS /D:TRANSCD$ /T:5
- The typical range for 'x' should be from 0 to 30, 0 being the fastest.
- If TCDGO is used to load the driver dynamically, simply append the 'x' to the
- command line where 'x' means the same thing as above. For example: TCDGO 5
-
- To find an optimum value, start with a number (say 5), move up or down
- until a lowest number is found where there is no problem. Then add 1 or 2 to
- it to provide additional safety margin and use that final number in "/T:x".
- It may be easier to try this experiment with TCDGO instead of DEVICE entry.
-
- If the TransCD is used with a large number of machines, consider using
- timing parameter ranging from 2 to 5 as standard. This provides
- much better compatibility across different machine platforms and in most
- cases avoids the need for tuning each machine individually.
-
- The performance degradation caused by the "/T" option should be relatively
- small given today's fast CPUs (486DX4/100, Pentium).
-